Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
pyparsing
version3.0.9
https://github.com/pyparsing/pyparsing/tree/pyparsing_3.0.9
python version >=3.6.8
https://github.com/pyparsing/pyparsing/blob/pyparsing_3.0.9/pyproject.toml#L11
flit-core >=3.2
https://github.com/pyparsing/pyparsing/blob/pyparsing_3.0.9/pyproject.toml#L2
https://github.com/pyparsing/pyparsing/blob/pyparsing_3.0.9/CHANGES
Version 3.0.9 -
Added Unicode set
BasicMultilingualPlane
(may also be referencedas
BMP
) representing the Basic Multilingual Plane (Unicodecharacters up to code point 65535). Can be used to parse
most language characters, but omits emojis, wingdings, etc.
Raised in discussion with Dave Tapley (issue #392).
Printables does not contain replacement character pyparsing/pyparsing#392
To address mypy confusion of
pyparsing.Optional
andtyping.Optional
resulting in
error: "_SpecialForm" not callable
messagereported in issue #365, fixed the import in exceptions.py. Nice
sleuthing by Iwan Aucamp and Dominic Davis-Foster, thank you!
(Removed definitions of
OptionalType
,DictType
, andIterableType
and replaced them with
typing.Optional
,typing.Dict
, andtyping.Iterable
throughout.)Typo in an example code pyparsing/pyparsing#365
Fixed typo in jinja2 template for railroad diagrams, thanks for the
catch Nioub (issue #388).
It's good to hear you are safe, but you are still missing your head pyparsing/pyparsing#388
Removed use of deprecated
pkg_resources
package inrailroad diagramming code (issue #391).
RFE: Replace use of
pkg_resources
withimportlib.metadata
pyparsing/pyparsing#391Updated bigquery_view_parser.py example to parse examples at
https://cloud.google.com/bigquery/docs/reference/legacy-sql
Version 3.0.8 -
API CHANGE: modified pyproject.toml to require Python version
3.6.8 or later for pyparsing 3.x. Earlier minor versions of 3.6
fail in evaluating the
version_info
class (implemented usingtyping.NamedTuple
). If you are using an earlier version of Python3.6, you will need to use pyparsing 2.4.7.
Improved pyparsing import time by deferring regex pattern compiles.
PR submitted by Anthony Sottile to fix issue #362, thanks!
3x import-time performance regression between 2.x and 3.x pyparsing/pyparsing#362
Updated build to use flit, PR by Michał Górny, added BUILDING.md
doc and removed old Windows build scripts - nice cleanup work!
More type-hinting added for all arithmetic and logical operator
methods in
ParserElement
. PR from Kazantcev Andrey, thank you.Fixed
infix_notation
's definitions oflpar
andrpar
, to acceptparse expressions such that they do not get suppressed in the parsed
results. PR submitted by Philippe Prados, nice work.
Fixed bug in railroad diagramming with expressions containing
Combine
elements. Reported by Jeremy White, thanks!
Added
show_groups
argument tocreate_diagram
to highlight groupedelements with an unlabeled bounding box.
Added
unicode_denormalizer.py
to the examples as a demonstrationof how Python's interpreter will accept Unicode characters in
identifiers, but normalizes them back to ASCII so that identifiers
print
and𝕡𝓻ᵢ𝓃𝘁
and𝖕𝒓𝗂𝑛ᵗ
are all equivalent.Removed imports of deprecated
sre_constants
module for catchingexceptions when compiling regular expressions. PR submitted by
Serhiy Storchaka, thank you.
Version 3.0.7 -
Fixed bug #345, in which delimitedList changed expressions in place
using
expr.streamline()
. Reported by Kim Gräsman, thanks!Parse actions skipped inside delimited_list pyparsing/pyparsing#345
Fixed bug #346, when a string of word characters was passed to WordStart
or
WordEnd
instead of just taking the default value. Originally postedas a question by Parag on StackOverflow, good catch!
Bug when defining WordStart with wordChars argument pyparsing/pyparsing#346
Fixed bug #350, in which
White
expressions could fail to match due tounintended whitespace-skipping. Reported by Fu Hanxi, thank you!
White
couldn't combine withset_results_name()
pyparsing/pyparsing#350Fixed bug #355, when a
QuotedString
is defined with characters in itsquoteChar string containing regex-significant characters such as ., *,
?, [, ], etc.
3.0 regression from 2.4.7 - regex generated for QuotedString pyparsing/pyparsing#355
Fixed bug in
ParserElement.run_tests
where comments would be displayedusing
with_line_numbers
.Added optional "min" and "max" arguments to
delimited_list
. PRsubmitted by Marius, thanks!
Added new API change note in
whats_new_in_pyparsing_3_0_0
, regardinga bug fix in the
bool()
behavior ofParseResults
.Prior to pyparsing 3.0.x, the
ParseResults
class implementation of__bool__
would returnFalse
if theParseResults
item list was empty,even if it contained named results. In 3.0.0 and later,
ParseResults
willreturn
True
if either the item list is not empty or if the namedresults dict is not empty.
Prints:
In previous versions, the second call to
bool()
would returnFalse
.Minor enhancement to Word generation of internal regular expression, to
emit consecutive characters in range, such as "ab", as "ab", not "a-b".
Fixed character ranges for search terms using non-Western characters
in booleansearchparser, PR submitted by tc-yu, nice work!
Additional type annotations on public methods.
Version 3.0.6 -
Added
suppress_warning()
method to individually suppress a warning on aspecific ParserElement. Used to refactor
original_text_for
to preserveinternal results names, which, while undocumented, had been adopted by
some projects.
Fix bug when
delimited_list
was called with a str literal instead of aparse expression.
Version 3.0.5 -
Added return type annotations for
col
,line
, andlineno
.Fixed bug when
warn_ungrouped_named_tokens_in_collection
warning was raisedwhen assigning a results name to an
original_text_for
expression.(Issue #110, would raise warning in packaging.)
unexpected "warn_ungrouped_named_tokens_in_collection" warnings in versions >2.4.0 pyparsing/pyparsing#110
Fixed internal bug where
ParserElement.streamline()
would not return self ifalready streamlined.
Changed
run_tests()
output to default to not showing line and column numbers.If line numbering is desired, call with
with_line_numbers=True
. Also fixedminor bug where separating line was not included after a test failure.
Version 3.0.4 -
Fixed bug in which
Dict
classes did not correctly return tokens as nestedParseResults
, reported by and fix identified by Bu Sun Kim, many thanks!!!Documented API-changing side-effect of converting
ParseResults
to use__slots__
to pre-define instance attributes. This means that code written like this (which
was allowed in pyparsing 2.4.7):
result = Word(alphas).parseString("abc")
result.xyz = 100
now raises this Python exception:
AttributeError: 'ParseResults' object has no attribute 'xyz'
To add new attribute values to ParseResults object in 3.0.0 and later, you must
assign them using indexed notation:
result["xyz"] = 100
You will still be able to access this new value as an attribute or as an
indexed item.
Fixed bug in railroad diagramming where the vertical limit would count all
expressions in a group, not just those that would create visible railroad
elements.
https://github.com/conda-forge/pyparsing-feedstock/issues
'version_info' object has no attribute '__version__' with python 3.6.0
'version_info' object has no attribute '__version__' with python 3.6.0 conda-forge/pyparsing-feedstock#36
Currently there is only one open issue for
python
version3.6.0
.However, since we no longer provide support for
python 3.6.0
we could conclude that there are no significant open issues mentioned that will affect the update of the package.dev_url
https://github.com/pyparsing/pyparsing/
doc_url
https://github.com/pyparsing/pyparsing/blob/master/docs/HowToUsePyparsing.rst
spdx
compliantMIT
MIT
build_number
is correctsetuptools
setuptools
wheel
wheel
pip
in the test sectionpip
architecture specific
orNoarch
Results:
Based on the research findings and the results we can conclude
that it is safe to update
pyparsing
to version3.0.9